Bug (hit during CLI testing)

🟢Query({"_type": "url", "verified": true})
[ERR] ai Action failed with error: AttributeError: 'str' object has no attribute 'items'
  File ".../secator/ai/actions.py", line 731, in _handle_query
    query_filter = _decrypt_dict(query_filter, ctx.encryptor)
  File ".../secator/ai/actions.py", line 1130, in _decrypt_dict
    for k, v in d.items()

The query_workspace tool schema correctly declares query as type: object, but the model returned it as a JSON string ('{"_type":"url","verified":true}') — a well-known tool-calling quirk where providers serialize nested object params as strings. _handle_query assumed a dict and handed it to _decrypt_dict, which does d.items() → AttributeError. It's caught by safe_dispatch_action (so non-fatal — the model retried with curl), but it wastes an iteration and any model that stringifies object args can never use query_workspace. (_decrypt_dict only fires when the encryptor is active, i.e. the default sensitive=True.)

Fix

• _handle_query: if query is a str, json.loads it before decrypt/search. On a non-JSON string or a non-dict, return a clean, LLM-actionable Error ("query must be a JSON object …") instead of crashing. Mirrors the existing add_finding scalar coercion.
• _decrypt_dict: no-op backstop on non-dict input.

Tests

TestHandleQuery: stringified query is coerced+searched with the encryptor active (the exact original crash condition); non-JSON string and non-dict each return one clean Error. TestDecryptDict: non-dict input returned unchanged. Full AI suite: no new failures vs branch baseline.

Found while testing ai-testing; targets ai-resiliency (#1241).

🤖 Generated with Claude Code